Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fae6f56ad04cdfd2a1bb553b26b1b49b0aec701a3eb5716f0a3e8991c50d4570

Tx prefix hash: fd68c5c1d1ce826dfdf8abc0ed89fcbb91370e1b5024ac4c9622930b4d7bd20a
Tx public key: be4f1657ffb475f16652f63adbfc058421575f2da17f665e8e20cf97e509036f
Timestamp: 1762232712 Timestamp [UCT]: 2025-11-04 05:05:12 Age [y:d:h:m:s]: 00:049:15:10:04
Block: 1404561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35536 RingCT/type: yes/0
Extra: 01be4f1657ffb475f16652f63adbfc058421575f2da17f665e8e20cf97e509036f02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb4ee25701d2dfd44a59775c98dbc8669fcd0ad77d2fb5815e8ec3004d3db391 0.600000000000 1892920 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": 1404571, "vin": [ { "gen": { "height": 1404561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb4ee25701d2dfd44a59775c98dbc8669fcd0ad77d2fb5815e8ec3004d3db391" } } ], "extra": [ 1, 190, 79, 22, 87, 255, 180, 117, 241, 102, 82, 246, 58, 219, 252, 5, 132, 33, 87, 95, 45, 161, 127, 102, 94, 142, 32, 207, 151, 229, 9, 3, 111, 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