Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bee2a9cad958963123f5786d0896370f996696fbb842d90317a84fccbe7b2fc3

Tx prefix hash: 26870c5d573144a6bdb4876e8cc28a67096bf08a543efec1b410812d481fd02e
Tx public key: ddc6d9acac550380c0145b80410cde02ba7c1b03f8f6363489bdea7fd2dcaace
Timestamp: 1714919646 Timestamp [UCT]: 2024-05-05 14:34:06 Age [y:d:h:m:s]: 00:193:12:18:05
Block: 1015445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138501 RingCT/type: yes/0
Extra: 01ddc6d9acac550380c0145b80410cde02ba7c1b03f8f6363489bdea7fd2dcaace02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa7a176b0b7b8eb2fefcf7e6681d679a2e196b2b7e2b2bcaaebf06fdb7adb5d0 0.600000000000 1478810 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": 1015455, "vin": [ { "gen": { "height": 1015445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa7a176b0b7b8eb2fefcf7e6681d679a2e196b2b7e2b2bcaaebf06fdb7adb5d0" } } ], "extra": [ 1, 221, 198, 217, 172, 172, 85, 3, 128, 192, 20, 91, 128, 65, 12, 222, 2, 186, 124, 27, 3, 248, 246, 54, 52, 137, 189, 234, 127, 210, 220, 170, 206, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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