Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad6fd5acfdfff274d9db8f4cb3476fd06fb76eae3dffcfa6f5bf39de9b39843f

Tx prefix hash: ff3b2509a044a666df42d8f1df2aab6a54270aebb253f19723efa473641e76f6
Tx public key: 04b3f9b2505e9e8f889cdb648d8dde0f99e59e46bca84c16aec5b0ca5bccb5bf
Timestamp: 1731521319 Timestamp [UCT]: 2024-11-13 18:08:39 Age [y:d:h:m:s]: 00:285:02:16:47
Block: 1152980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201377 RingCT/type: yes/0
Extra: 0104b3f9b2505e9e8f889cdb648d8dde0f99e59e46bca84c16aec5b0ca5bccb5bf021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4ad98ef28f1c657ef0e87c5ea0b9dbaaed0c528d858294e5523e059daca3692 0.600000000000 1638587 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": 1152990, "vin": [ { "gen": { "height": 1152980 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4ad98ef28f1c657ef0e87c5ea0b9dbaaed0c528d858294e5523e059daca3692" } } ], "extra": [ 1, 4, 179, 249, 178, 80, 94, 158, 143, 136, 156, 219, 100, 141, 141, 222, 15, 153, 229, 158, 70, 188, 168, 76, 22, 174, 197, 176, 202, 91, 204, 181, 191, 2, 17, 0, 0, 0, 3, 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