Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8703bb423927e67fdc356c8e94eff4af2eea5d1e8a5dd457342961d906526278

Tx prefix hash: 887f8b224d1982b9e8143d686636cd1b4f52e76ce944907205ab8455ba21ce10
Tx public key: bf61fccce6058581a22f17b1f028d80181ed639e3d4b1f0b1ccc0c4b3d4f644d
Timestamp: 1763163930 Timestamp [UCT]: 2025-11-14 23:45:30 Age [y:d:h:m:s]: 00:049:15:09:14
Block: 1412279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35546 RingCT/type: yes/0
Extra: 01bf61fccce6058581a22f17b1f028d80181ed639e3d4b1f0b1ccc0c4b3d4f644d02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b90ae9cd557d05a33cb342da18b1b62dcc74cb51672606770d1d2127261bb6ed 0.600000000000 1900746 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": 1412289, "vin": [ { "gen": { "height": 1412279 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b90ae9cd557d05a33cb342da18b1b62dcc74cb51672606770d1d2127261bb6ed" } } ], "extra": [ 1, 191, 97, 252, 204, 230, 5, 133, 129, 162, 47, 23, 177, 240, 40, 216, 1, 129, 237, 99, 158, 61, 75, 31, 11, 28, 204, 12, 75, 61, 79, 100, 77, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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