Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31728f802f2d3c1ca433d307a1b6d76cc7d94e561e9df6997dc79b46edb7b3ed

Tx prefix hash: ac78af637eedfdbf69fd8ebf8570521eb31f1acefe62a8e1b15077dcbc47ce3f
Tx public key: ddf994479a8c8e488eae160c9c4f3d34c7fa55b33f8c291af79eb3b2c3f2e89f
Timestamp: 1744576186 Timestamp [UCT]: 2025-04-13 20:29:46 Age [y:d:h:m:s]: 00:221:06:38:44
Block: 1260804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155857 RingCT/type: yes/0
Extra: 01ddf994479a8c8e488eae160c9c4f3d34c7fa55b33f8c291af79eb3b2c3f2e89f021100000003dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c0330084213de28e3d37e6fcd08eb89f26dd1f7e02915a728b329e11744f19d 0.600000000000 1747967 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": 1260814, "vin": [ { "gen": { "height": 1260804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c0330084213de28e3d37e6fcd08eb89f26dd1f7e02915a728b329e11744f19d" } } ], "extra": [ 1, 221, 249, 148, 71, 154, 140, 142, 72, 142, 174, 22, 12, 156, 79, 61, 52, 199, 250, 85, 179, 63, 140, 41, 26, 247, 158, 179, 178, 195, 242, 232, 159, 2, 17, 0, 0, 0, 3, 219, 181, 113, 193, 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