Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 886fd364dc7fa53f5eaffc1e986614861b2d85e9089d99545343587f62c5348d

Tx prefix hash: 20e209f9d64cd410375b4115629bb239ff25301e1b80f2081b67bdc0045b6af1
Tx public key: 3aa14a10f68f1807b63986d4bae21b9f1ab6fde198fb1722917b8a2747cea409
Timestamp: 1721252836 Timestamp [UCT]: 2024-07-17 21:47:16 Age [y:d:h:m:s]: 00:266:00:17:44
Block: 1067955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190029 RingCT/type: yes/0
Extra: 013aa14a10f68f1807b63986d4bae21b9f1ab6fde198fb1722917b8a2747cea40902110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce535e9fd8cd98ef0057496f0b529de4b6d1558169daa804cbf0033d1b059a52 0.600000000000 1538912 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": 1067965, "vin": [ { "gen": { "height": 1067955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce535e9fd8cd98ef0057496f0b529de4b6d1558169daa804cbf0033d1b059a52" } } ], "extra": [ 1, 58, 161, 74, 16, 246, 143, 24, 7, 182, 57, 134, 212, 186, 226, 27, 159, 26, 182, 253, 225, 152, 251, 23, 34, 145, 123, 138, 39, 71, 206, 164, 9, 2, 17, 0, 0, 0, 11, 145, 225, 60, 4, 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