Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22a8f87e3253668ed9f596f21c45b51ec1f636232fe7885dfec634eef5d48b62

Tx prefix hash: 56336517fffb1e13875d710e3c01af0990a72344982c94551a8c9767192beef4
Tx public key: e721590bf32a5ebb69c6b3503a90fc85ca7e25c9da831aa69c2a2f29d004208e
Timestamp: 1693226569 Timestamp [UCT]: 2023-08-28 12:42:49 Age [y:d:h:m:s]: 01:210:17:08:08
Block: 835756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411720 RingCT/type: yes/0
Extra: 01e721590bf32a5ebb69c6b3503a90fc85ca7e25c9da831aa69c2a2f29d004208e02110000000527f2911c000000000000000000

1 output(s) for total of 1.044223615000 dcy

stealth address amount amount idx
00: 84d3d0391551614d21c1a7fd9e335229ee33730e86a7e2e941eaf080d8c81212 1.044223615000 1288324 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": 835766, "vin": [ { "gen": { "height": 835756 } } ], "vout": [ { "amount": 1044223615, "target": { "key": "84d3d0391551614d21c1a7fd9e335229ee33730e86a7e2e941eaf080d8c81212" } } ], "extra": [ 1, 231, 33, 89, 11, 243, 42, 94, 187, 105, 198, 179, 80, 58, 144, 252, 133, 202, 126, 37, 201, 218, 131, 26, 166, 156, 42, 47, 41, 208, 4, 32, 142, 2, 17, 0, 0, 0, 5, 39, 242, 145, 28, 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