Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e61b331a34cb5518f49ab9e8b7847fe44388f6b886f3ca5e8fb559b17a613899

Tx prefix hash: dfa1a80b263dc8053ee95de6a19ef2be4eb757438d6397eace9f5b1f6be4abb7
Tx public key: 8a419de734d2be9918d38dcd179fe4ee16cacb517d2608e91f3610c9473653b6
Timestamp: 1706842859 Timestamp [UCT]: 2024-02-02 03:00:59 Age [y:d:h:m:s]: 00:264:11:27:22
Block: 948463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189424 RingCT/type: yes/0
Extra: 018a419de734d2be9918d38dcd179fe4ee16cacb517d2608e91f3610c9473653b602110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17c0f57daadf0fd87b8c7dc2efd2ce2ea73083d6dd94221a5a93a912238ca7eb 0.600000000000 1406877 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": 948473, "vin": [ { "gen": { "height": 948463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17c0f57daadf0fd87b8c7dc2efd2ce2ea73083d6dd94221a5a93a912238ca7eb" } } ], "extra": [ 1, 138, 65, 157, 231, 52, 210, 190, 153, 24, 211, 141, 205, 23, 159, 228, 238, 22, 202, 203, 81, 125, 38, 8, 233, 31, 54, 16, 201, 71, 54, 83, 182, 2, 17, 0, 0, 0, 6, 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