Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b438b1c8d64b59dc32113ca0eca9650c08dad23955fd1c4510899434f0ad8d9f

Tx prefix hash: a41f72b160fc2803496089c266d9c37e39380d175818f534764d85cb59e282e4
Tx public key: 2ada05e46d3955a49db50e388f8a2e8ea0ba9462d659ea97620991fd2c3b9f89
Timestamp: 1748658704 Timestamp [UCT]: 2025-05-31 02:31:44 Age [y:d:h:m:s]: 00:162:01:26:07
Block: 1294605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113504 RingCT/type: yes/0
Extra: 012ada05e46d3955a49db50e388f8a2e8ea0ba9462d659ea97620991fd2c3b9f890211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1cc6c6298bee59ba19bc29ff215fa1c04d6f1a722e12769b23117c6c448bf50 0.600000000000 1782100 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": 1294615, "vin": [ { "gen": { "height": 1294605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1cc6c6298bee59ba19bc29ff215fa1c04d6f1a722e12769b23117c6c448bf50" } } ], "extra": [ 1, 42, 218, 5, 228, 109, 57, 85, 164, 157, 181, 14, 56, 143, 138, 46, 142, 160, 186, 148, 98, 214, 89, 234, 151, 98, 9, 145, 253, 44, 59, 159, 137, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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