Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e05b3fc0c928ddacf259531d6f9f83d6b60613ee2d68bfdaa75f1ec0690acdc

Tx prefix hash: bd03eb5a19652b0791a82adb08f5e595e6cbe5a370fca1e66bc6ed3f67a2a1e3
Tx public key: 00a17b3a3235ee6e94ca2ec280081044c3cc4be6e5860eddcb07fb368ca57808
Timestamp: 1730526393 Timestamp [UCT]: 2024-11-02 05:46:33 Age [y:d:h:m:s]: 00:022:13:02:30
Block: 1144737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16136 RingCT/type: yes/0
Extra: 0100a17b3a3235ee6e94ca2ec280081044c3cc4be6e5860eddcb07fb368ca57808021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2673eedb4138ab3f13fd8b97af5793d2edc797ad9aaefd458fa35def0c0e14ea 0.600000000000 1629028 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": 1144747, "vin": [ { "gen": { "height": 1144737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2673eedb4138ab3f13fd8b97af5793d2edc797ad9aaefd458fa35def0c0e14ea" } } ], "extra": [ 1, 0, 161, 123, 58, 50, 53, 238, 110, 148, 202, 46, 194, 128, 8, 16, 68, 195, 204, 75, 230, 229, 134, 14, 221, 203, 7, 251, 54, 140, 165, 120, 8, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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