Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d82a59e251dcac799c214517c5471f842da8cad4ba8a8654e21091c444ef28

Tx prefix hash: 601ca25c264d4e5f6153937d1f25895f10fa9bc0d7a083265430e82ec127421a
Tx public key: 43a0874ddced44673b315bf3ea2417917b26d19e794caf07c5e02b3cfcfcdc57
Timestamp: 1751403729 Timestamp [UCT]: 2025-07-01 21:02:09 Age [y:d:h:m:s]: 00:139:16:03:17
Block: 1316778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98041 RingCT/type: yes/0
Extra: 0143a0874ddced44673b315bf3ea2417917b26d19e794caf07c5e02b3cfcfcdc570211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f0fbb3b8718008e0e2e3c7a623a959c0d3f423ae638d8353c5a9a26e6bfa7b1 0.600000000000 1804441 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": 1316788, "vin": [ { "gen": { "height": 1316778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f0fbb3b8718008e0e2e3c7a623a959c0d3f423ae638d8353c5a9a26e6bfa7b1" } } ], "extra": [ 1, 67, 160, 135, 77, 220, 237, 68, 103, 59, 49, 91, 243, 234, 36, 23, 145, 123, 38, 209, 158, 121, 76, 175, 7, 197, 224, 43, 60, 252, 252, 220, 87, 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