Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d798062b5508e7f3d2af87b7b4a351b5b6ca4de781bfbcd0f3e8368dcd1f9ddd

Tx prefix hash: 814def19468810c107757254ba0a145e2784c6058a201412e517201a5f9b4e04
Tx public key: 7745c3c4396c5c9bb6e30726db767ec96d241029881adac8c6e16c3ef415bdd8
Timestamp: 1706944301 Timestamp [UCT]: 2024-02-03 07:11:41 Age [y:d:h:m:s]: 00:285:11:02:50
Block: 949301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204403 RingCT/type: yes/0
Extra: 017745c3c4396c5c9bb6e30726db767ec96d241029881adac8c6e16c3ef415bdd80211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5195c4caf48f190da416422373e2c4a046696007b560f85872d800a28dd06cb8 0.600000000000 1407825 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": 949311, "vin": [ { "gen": { "height": 949301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5195c4caf48f190da416422373e2c4a046696007b560f85872d800a28dd06cb8" } } ], "extra": [ 1, 119, 69, 195, 196, 57, 108, 92, 155, 182, 227, 7, 38, 219, 118, 126, 201, 109, 36, 16, 41, 136, 26, 218, 200, 198, 225, 108, 62, 244, 21, 189, 216, 2, 17, 0, 0, 0, 8, 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