Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a48ffba4ceaa0c04f08a47526bd7cd1e47c0490a4cfb0ba02a1cbe54bcd16f8a

Tx prefix hash: a8f1c059821e34024aba4b22f8ff5c1789e9a085f14e4909824dd6c666ac12d5
Tx public key: 4f69ce703afd02210ac38390bb44c63285a1e20493b5a9c4e73d93d5b63746ea
Timestamp: 1736211681 Timestamp [UCT]: 2025-01-07 01:01:21 Age [y:d:h:m:s]: 00:162:20:00:18
Block: 1191817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116072 RingCT/type: yes/0
Extra: 014f69ce703afd02210ac38390bb44c63285a1e20493b5a9c4e73d93d5b63746ea021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: edc79dbf3355d592244efc92f0f8ac827fd41d64a70c6ff19968bcb678889822 0.600000000000 1678360 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": 1191827, "vin": [ { "gen": { "height": 1191817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edc79dbf3355d592244efc92f0f8ac827fd41d64a70c6ff19968bcb678889822" } } ], "extra": [ 1, 79, 105, 206, 112, 58, 253, 2, 33, 10, 195, 131, 144, 187, 68, 198, 50, 133, 161, 226, 4, 147, 181, 169, 196, 231, 61, 147, 213, 182, 55, 70, 234, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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