Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 828bea1789084e4e4d3bcb4fc36279ed476ac2cea75ac8e39602120d4f694a7e

Tx prefix hash: f5e15c5a5784fde40d0d99013f91aecb4b114a39c545e1eab356d3d3ac673319
Tx public key: c6b20f5a6553b883afe4925654cd2913d1b301c3d143ab4d0a3c74bbe80a0440
Timestamp: 1758090133 Timestamp [UCT]: 2025-09-17 06:22:13 Age [y:d:h:m:s]: 00:103:21:21:58
Block: 1370228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74387 RingCT/type: yes/0
Extra: 01c6b20f5a6553b883afe4925654cd2913d1b301c3d143ab4d0a3c74bbe80a0440021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fbea60d9443a8696d16babad399266e76bae6982990fb7fb5ea200cdc0e829d 0.600000000000 1858303 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": 1370238, "vin": [ { "gen": { "height": 1370228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fbea60d9443a8696d16babad399266e76bae6982990fb7fb5ea200cdc0e829d" } } ], "extra": [ 1, 198, 178, 15, 90, 101, 83, 184, 131, 175, 228, 146, 86, 84, 205, 41, 19, 209, 179, 1, 195, 209, 67, 171, 77, 10, 60, 116, 187, 232, 10, 4, 64, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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