Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14709ce75e9096275939eb6bc90dff27285c842008ec84f5620b96d56aaa0f5a

Tx prefix hash: 9701f0637399541846874eea7df0de06f26b8cc6ba7679e6d6a23bbc46156f78
Tx public key: 843b46a8b809ac1e2e1b44a2c824e1dbaff345c9dae8f37729504a9a80b61735
Timestamp: 1592761168 Timestamp [UCT]: 2020-06-21 17:39:28 Age [y:d:h:m:s]: 04:138:06:22:13
Block: 110167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1037256 RingCT/type: yes/0
Extra: 01843b46a8b809ac1e2e1b44a2c824e1dbaff345c9dae8f37729504a9a80b6173502110000002646a11e8a000000000000000000

1 output(s) for total of 264.832782974000 dcy

stealth address amount amount idx
00: 9d52533929037edf49512ff98b0b68e5a325807dba47899a776a69e92cd34d5c 264.832782974000 190799 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": 110177, "vin": [ { "gen": { "height": 110167 } } ], "vout": [ { "amount": 264832782974, "target": { "key": "9d52533929037edf49512ff98b0b68e5a325807dba47899a776a69e92cd34d5c" } } ], "extra": [ 1, 132, 59, 70, 168, 184, 9, 172, 30, 46, 27, 68, 162, 200, 36, 225, 219, 175, 243, 69, 201, 218, 232, 243, 119, 41, 80, 74, 154, 128, 182, 23, 53, 2, 17, 0, 0, 0, 38, 70, 161, 30, 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