Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45e44733efe27a88f5c09da48819fef6b0ef35ed323510ec66d84063ed745918

Tx prefix hash: 23c69bef1dc3ad5f5b6467c7850f4bf641d1e5aec85017a0e1b30486d4cf2243
Tx public key: 572b15e17532932e4c2a0904e7cde34aa2295d3b7a2cb391bcbabf20988ffbcf
Timestamp: 1745527877 Timestamp [UCT]: 2025-04-24 20:51:17 Age [y:d:h:m:s]: 00:207:17:19:12
Block: 1268684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146174 RingCT/type: yes/0
Extra: 01572b15e17532932e4c2a0904e7cde34aa2295d3b7a2cb391bcbabf20988ffbcf0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 492b6d1d00f8686e0dfb31d42aed13ea39b0117542a190f143f16f58bd140752 0.600000000000 1755915 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": 1268694, "vin": [ { "gen": { "height": 1268684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "492b6d1d00f8686e0dfb31d42aed13ea39b0117542a190f143f16f58bd140752" } } ], "extra": [ 1, 87, 43, 21, 225, 117, 50, 147, 46, 76, 42, 9, 4, 231, 205, 227, 74, 162, 41, 93, 59, 122, 44, 179, 145, 188, 186, 191, 32, 152, 143, 251, 207, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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