Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: babb8e67f11c6753c20b42cf1a91e63890c245bf6fb1ef0ff6467a94ff1d34d9

Tx prefix hash: 3f6d3474ee9b247cd6f223035517c764e7fd063b298c46106a25b7d1f2395a86
Tx public key: 3da71ebef91e0bede5c1d70b8db5d7981405e80897e5f84dacc80d6d106f7ddd
Timestamp: 1713728645 Timestamp [UCT]: 2024-04-21 19:44:05 Age [y:d:h:m:s]: 00:216:14:51:05
Block: 1005550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155076 RingCT/type: yes/0
Extra: 013da71ebef91e0bede5c1d70b8db5d7981405e80897e5f84dacc80d6d106f7ddd0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6887880105bb5df5c0e8e5fbf6da2c88c41e7f442d0b3635e5349bc726608291 0.600000000000 1466280 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": 1005560, "vin": [ { "gen": { "height": 1005550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6887880105bb5df5c0e8e5fbf6da2c88c41e7f442d0b3635e5349bc726608291" } } ], "extra": [ 1, 61, 167, 30, 190, 249, 30, 11, 237, 229, 193, 215, 11, 141, 181, 215, 152, 20, 5, 232, 8, 151, 229, 248, 77, 172, 200, 13, 109, 16, 111, 125, 221, 2, 17, 0, 0, 0, 5, 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