Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b30a649564f7fd0518c2f7d795d2a9aad87a7cb78ff7f0da0c0e31985ce0de84

Tx prefix hash: ee28102aaca0dc53c100235d62723092c0d4d9596ab86bb55149364db13822d8
Tx public key: 067ea243ce0b6d05f960f0c6aa2597bed154a572b6e8f2d5fdcba22373aadb8d
Timestamp: 1745822130 Timestamp [UCT]: 2025-04-28 06:35:30 Age [y:d:h:m:s]: 00:052:10:02:55
Block: 1271127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 37360 RingCT/type: yes/0
Extra: 01067ea243ce0b6d05f960f0c6aa2597bed154a572b6e8f2d5fdcba22373aadb8d0211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f588cfc0d6200abf785d81ad5488441e47aad5eb75c96fce74c0618339ada71 0.600000000000 1758378 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": 1271137, "vin": [ { "gen": { "height": 1271127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f588cfc0d6200abf785d81ad5488441e47aad5eb75c96fce74c0618339ada71" } } ], "extra": [ 1, 6, 126, 162, 67, 206, 11, 109, 5, 249, 96, 240, 198, 170, 37, 151, 190, 209, 84, 165, 114, 182, 232, 242, 213, 253, 203, 162, 35, 115, 170, 219, 141, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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