Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37b28c5211cd46172f133b27c1a67286da1de0e4c4818e9d713e1772ff0e1a2b

Tx prefix hash: 35a0f7776d8d6035f79a19a9919c97cc180bb22e4494d926a7682006a1b0bc89
Tx public key: e8b1d26c981bfafb86ab5483d09ab18d9b41aa5657868c5dfb4dd065827e5c74
Timestamp: 1709584897 Timestamp [UCT]: 2024-03-04 20:41:37 Age [y:d:h:m:s]: 01:254:07:14:06
Block: 971222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440470 RingCT/type: yes/0
Extra: 01e8b1d26c981bfafb86ab5483d09ab18d9b41aa5657868c5dfb4dd065827e5c740211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efae729a9d941b92f9cd0b89097e284b2008ad9afa9e4b14d62478ed8c919ad7 0.600000000000 1431109 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": 971232, "vin": [ { "gen": { "height": 971222 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efae729a9d941b92f9cd0b89097e284b2008ad9afa9e4b14d62478ed8c919ad7" } } ], "extra": [ 1, 232, 177, 210, 108, 152, 27, 250, 251, 134, 171, 84, 131, 208, 154, 177, 141, 155, 65, 170, 86, 87, 134, 140, 93, 251, 77, 208, 101, 130, 126, 92, 116, 2, 17, 0, 0, 0, 1, 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