Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b192f475495b49d0a339f971b7058fd77b01693517edb5e5025631ffcae350e

Tx prefix hash: 4852596ad0c6929aadec7297a3bc02945fdb1b1265fb9116911e12e9641907ac
Tx public key: a70d7928c051137200d047e7c59e96465ddee7df8de6e0f2a251a5120d7b290f
Timestamp: 1681613019 Timestamp [UCT]: 2023-04-16 02:43:39 Age [y:d:h:m:s]: 01:351:06:58:28
Block: 739551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512332 RingCT/type: yes/0
Extra: 01a70d7928c051137200d047e7c59e96465ddee7df8de6e0f2a251a5120d7b290f02110000000b75e3f0e9000000000000000000

1 output(s) for total of 2.175508343000 dcy

stealth address amount amount idx
00: 076651579ab1403e5b701159c382faf8c9fda3831873ea31aeead71a9fefbeef 2.175508343000 1186406 of 0

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": 739561, "vin": [ { "gen": { "height": 739551 } } ], "vout": [ { "amount": 2175508343, "target": { "key": "076651579ab1403e5b701159c382faf8c9fda3831873ea31aeead71a9fefbeef" } } ], "extra": [ 1, 167, 13, 121, 40, 192, 81, 19, 114, 0, 208, 71, 231, 197, 158, 150, 70, 93, 222, 231, 223, 141, 230, 224, 242, 162, 81, 165, 18, 13, 123, 41, 15, 2, 17, 0, 0, 0, 11, 117, 227, 240, 233, 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