Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aabc4e55bd39fea456dcaadb76ee1e9005a6b7ea5d3421667a71f721a6fb7cab

Tx prefix hash: 1fbc3da3dde9ea7523c483820c0fbccb6080eadd6d784b90224ab1b84d44fa8b
Tx public key: 587117ae1851b436053c5b126d772ba323be54cee815aafe3bce35af41fe395e
Timestamp: 1746035479 Timestamp [UCT]: 2025-04-30 17:51:19 Age [y:d:h:m:s]: 00:204:09:18:34
Block: 1272881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143781 RingCT/type: yes/0
Extra: 01587117ae1851b436053c5b126d772ba323be54cee815aafe3bce35af41fe395e0211000000019f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48ab6f04e3485850c0d1103a9aed4f3bc052dbd29e9cfd666f4698bdb3b594a2 0.600000000000 1760158 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": 1272891, "vin": [ { "gen": { "height": 1272881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48ab6f04e3485850c0d1103a9aed4f3bc052dbd29e9cfd666f4698bdb3b594a2" } } ], "extra": [ 1, 88, 113, 23, 174, 24, 81, 180, 54, 5, 60, 91, 18, 109, 119, 43, 163, 35, 190, 84, 206, 232, 21, 170, 254, 59, 206, 53, 175, 65, 254, 57, 94, 2, 17, 0, 0, 0, 1, 159, 159, 230, 140, 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