Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eb7cbb561f233db6d6b14959128b70bbb89ea12a2623da758383cea6a0c57e6

Tx prefix hash: c8015348f25645aa00478ba0dd54a17f38f375f6bb4b473ecbcc810c35d85988
Tx public key: 1d4b7b51c9fb424bbc6ac69565300d2ba960020e67cc6c49af24d4fb0699bab9
Timestamp: 1719960201 Timestamp [UCT]: 2024-07-02 22:43:21 Age [y:d:h:m:s]: 00:282:04:45:55
Block: 1057219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201648 RingCT/type: yes/0
Extra: 011d4b7b51c9fb424bbc6ac69565300d2ba960020e67cc6c49af24d4fb0699bab90211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46ce2e0fc2646fe124e97c96fdd55d89b4cbd8b80d2e27b3fe8a5c052dd0f4ba 0.600000000000 1527652 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": 1057229, "vin": [ { "gen": { "height": 1057219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46ce2e0fc2646fe124e97c96fdd55d89b4cbd8b80d2e27b3fe8a5c052dd0f4ba" } } ], "extra": [ 1, 29, 75, 123, 81, 201, 251, 66, 75, 188, 106, 198, 149, 101, 48, 13, 43, 169, 96, 2, 14, 103, 204, 108, 73, 175, 36, 212, 251, 6, 153, 186, 185, 2, 17, 0, 0, 0, 2, 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