Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e86a266d8a95b51fd5a0583fb07a98c9fd9e613c3e5624664c7b171a7da8b5b6

Tx prefix hash: 5361f41fa38a678167968ddb110c9de0b5671548621d10db2614a6fb7b5a18c0
Tx public key: 46af8402c0845ee87f18283dcef91549a95dbcf2728a54e1faff084882a2902e
Timestamp: 1700070739 Timestamp [UCT]: 2023-11-15 17:52:19 Age [y:d:h:m:s]: 01:143:06:31:51
Block: 892334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363561 RingCT/type: yes/0
Extra: 0146af8402c0845ee87f18283dcef91549a95dbcf2728a54e1faff084882a2902e02110000000133af99f4000000000000000000

1 output(s) for total of 0.678151969000 dcy

stealth address amount amount idx
00: 03309883bdc509a37b599f0da19f66fc995a0ce339829e802d0cc56dca3b825a 0.678151969000 1348453 of 0

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": 892344, "vin": [ { "gen": { "height": 892334 } } ], "vout": [ { "amount": 678151969, "target": { "key": "03309883bdc509a37b599f0da19f66fc995a0ce339829e802d0cc56dca3b825a" } } ], "extra": [ 1, 70, 175, 132, 2, 192, 132, 94, 232, 127, 24, 40, 61, 206, 249, 21, 73, 169, 93, 188, 242, 114, 138, 84, 225, 250, 255, 8, 72, 130, 162, 144, 46, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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