Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 496a74f5995a3383c7cfe25df7a6fa684e576bcf14466fde011ba5fb7ccfb4f0

Tx prefix hash: 5b2e6a59760ec9c735e06bba5ab946ab8f810c49880d69b5ceabe11002a8798d
Tx public key: 43d2d62e07d82018a4af289b0f2d4d57341487f838d9e048dada666e8c2f8bda
Timestamp: 1715666476 Timestamp [UCT]: 2024-05-14 06:01:16 Age [y:d:h:m:s]: 00:224:20:09:53
Block: 1021629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160944 RingCT/type: yes/0
Extra: 0143d2d62e07d82018a4af289b0f2d4d57341487f838d9e048dada666e8c2f8bda0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8629191c4c973a2227b1230d74318effc2f0c9d0c814110ce76e35defdfcfdb8 0.600000000000 1486002 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": 1021639, "vin": [ { "gen": { "height": 1021629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8629191c4c973a2227b1230d74318effc2f0c9d0c814110ce76e35defdfcfdb8" } } ], "extra": [ 1, 67, 210, 214, 46, 7, 216, 32, 24, 164, 175, 40, 155, 15, 45, 77, 87, 52, 20, 135, 248, 56, 217, 224, 72, 218, 218, 102, 110, 140, 47, 139, 218, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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