Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 986483c0b5a8eefc94b7e4c74abbc2519c02c398aa4ccee94f6dc33cf79bd183

Tx prefix hash: fe219c7c31f115e35d437d11afbe99a1f9048caf3543e1f76052c402f06906d9
Tx public key: 4a11ffcf4d0ed8f22a5a84f2219f63f7e51244ad9d2c78a6f3e4e734d1a82407
Timestamp: 1720041107 Timestamp [UCT]: 2024-07-03 21:11:47 Age [y:d:h:m:s]: 00:313:00:51:15
Block: 1057889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223701 RingCT/type: yes/0
Extra: 014a11ffcf4d0ed8f22a5a84f2219f63f7e51244ad9d2c78a6f3e4e734d1a824070211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbe757114217987c06fe77911e27f2a91c4bccd62dc7b52e68dfa47f3716bc47 0.600000000000 1528332 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": 1057899, "vin": [ { "gen": { "height": 1057889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbe757114217987c06fe77911e27f2a91c4bccd62dc7b52e68dfa47f3716bc47" } } ], "extra": [ 1, 74, 17, 255, 207, 77, 14, 216, 242, 42, 90, 132, 242, 33, 159, 99, 247, 229, 18, 68, 173, 157, 44, 120, 166, 243, 228, 231, 52, 209, 168, 36, 7, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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