Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92f4843f70564d98119c432bed43a4b1e0500a42794e194fa6f52ae1e1bf9a19

Tx prefix hash: badaed972cd48d44321fef30c97acc5f984fb8714a2e28006cded1116f2c415d
Tx public key: 412f67ea89c76d90054832b1145f702342398e2abbb1e98d1036e79e8f7c1f1d
Timestamp: 1708320366 Timestamp [UCT]: 2024-02-19 05:26:06 Age [y:d:h:m:s]: 01:307:08:17:31
Block: 960724 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478463 RingCT/type: yes/0
Extra: 01412f67ea89c76d90054832b1145f702342398e2abbb1e98d1036e79e8f7c1f1d0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f680741517d6cc17c74edc814c863a1b0acc4c3652f66bcf89a6f828cd1e86f 0.600000000000 1420311 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": 960734, "vin": [ { "gen": { "height": 960724 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f680741517d6cc17c74edc814c863a1b0acc4c3652f66bcf89a6f828cd1e86f" } } ], "extra": [ 1, 65, 47, 103, 234, 137, 199, 109, 144, 5, 72, 50, 177, 20, 95, 112, 35, 66, 57, 142, 42, 187, 177, 233, 141, 16, 54, 231, 158, 143, 124, 31, 29, 2, 17, 0, 0, 0, 3, 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