Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99b7c75b9f4a85b8d71f5925e2bc1e69feb7002ddd55a326b2522f2460208a1c

Tx prefix hash: 4f8768f4c0d7c69a76d61b80296f87317f57ca23a496475a2ea3bf808158f34a
Tx public key: 60e231f9ac298989bc03ff02310ca721100af67983d6fecef5dc94f7aa7d0714
Timestamp: 1706813594 Timestamp [UCT]: 2024-02-01 18:53:14 Age [y:d:h:m:s]: 01:071:10:33:20
Block: 948218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312133 RingCT/type: yes/0
Extra: 0160e231f9ac298989bc03ff02310ca721100af67983d6fecef5dc94f7aa7d071402110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32ae68e1b7d0f9989cc50b60f2e7031b47c2aee3a74515f24bb7d58fae0e0946 0.600000000000 1406592 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": 948228, "vin": [ { "gen": { "height": 948218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32ae68e1b7d0f9989cc50b60f2e7031b47c2aee3a74515f24bb7d58fae0e0946" } } ], "extra": [ 1, 96, 226, 49, 249, 172, 41, 137, 137, 188, 3, 255, 2, 49, 12, 167, 33, 16, 10, 246, 121, 131, 214, 254, 206, 245, 220, 148, 247, 170, 125, 7, 20, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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