Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae9fc74e5b98b576a4a167a9bc6e52ebfbd81000d8d4984cebbdb8484569828b

Tx prefix hash: df42ed96f8f5b3bb9d375babf423dd0bf5f0840257f3cd9139c3fee3978cb14d
Tx public key: c6bbc370080c36562e4dc95c1cbffd69839ae502401d0350838de40264baff1f
Timestamp: 1708323191 Timestamp [UCT]: 2024-02-19 06:13:11 Age [y:d:h:m:s]: 01:123:13:03:05
Block: 960746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349211 RingCT/type: yes/0
Extra: 01c6bbc370080c36562e4dc95c1cbffd69839ae502401d0350838de40264baff1f0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56e5e8ed2d0f4dcddbabb2e2ffb95f0b34b7943ed82a3fa28948c94f954b9a15 0.600000000000 1420333 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": 960756, "vin": [ { "gen": { "height": 960746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56e5e8ed2d0f4dcddbabb2e2ffb95f0b34b7943ed82a3fa28948c94f954b9a15" } } ], "extra": [ 1, 198, 187, 195, 112, 8, 12, 54, 86, 46, 77, 201, 92, 28, 191, 253, 105, 131, 154, 229, 2, 64, 29, 3, 80, 131, 141, 228, 2, 100, 186, 255, 31, 2, 17, 0, 0, 0, 6, 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