Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3bf729eaac44659165adbdb430a58740916aa2f82d8d1c19fcac72f6d0282a26

Tx prefix hash: 3617ff8f03ab19d2612277e7de2307ba552bb05c76fddb4dcb2e8fb2f3cc7682
Tx public key: f94c8d925ee8bf8a889a14952e28a279dd0976d5e5c43518334d4c03ad60a4a1
Timestamp: 1737119235 Timestamp [UCT]: 2025-01-17 13:07:15 Age [y:d:h:m:s]: 00:151:23:24:39
Block: 1199334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108323 RingCT/type: yes/0
Extra: 01f94c8d925ee8bf8a889a14952e28a279dd0976d5e5c43518334d4c03ad60a4a1021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e6c92e05b2bc803c92eb30e4e00901c885ae23f5af165c9b56faf0ba44a4d82 0.600000000000 1685965 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1199344, "vin": [ { "gen": { "height": 1199334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e6c92e05b2bc803c92eb30e4e00901c885ae23f5af165c9b56faf0ba44a4d82" } } ], "extra": [ 1, 249, 76, 141, 146, 94, 232, 191, 138, 136, 154, 20, 149, 46, 40, 162, 121, 221, 9, 118, 213, 229, 196, 53, 24, 51, 77, 76, 3, 173, 96, 164, 161, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8