Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46a093a2c377531c11aa34cdb5f4f2c79b1afe136752aa80278b343f6c648eb5

Tx prefix hash: 4fd0b4d8eb72c2542484186e54ac1ae1a174a4680ec096640a53c1669f6bb6c9
Tx public key: 206147e97773af4fe256a7c9983bf1f15316813971e0d0a9b6eef5c2ea29713e
Timestamp: 1733215375 Timestamp [UCT]: 2024-12-03 08:42:55 Age [y:d:h:m:s]: 00:121:21:56:58
Block: 1167015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86936 RingCT/type: yes/0
Extra: 01206147e97773af4fe256a7c9983bf1f15316813971e0d0a9b6eef5c2ea29713e021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31433c9c68fcc8cf7a578ff991e7b393fffd194b79de545875365ecdc3a71716 0.600000000000 1652708 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": 1167025, "vin": [ { "gen": { "height": 1167015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31433c9c68fcc8cf7a578ff991e7b393fffd194b79de545875365ecdc3a71716" } } ], "extra": [ 1, 32, 97, 71, 233, 119, 115, 175, 79, 226, 86, 167, 201, 152, 59, 241, 241, 83, 22, 129, 57, 113, 224, 208, 169, 182, 238, 245, 194, 234, 41, 113, 62, 2, 17, 0, 0, 0, 4, 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