Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1acb64a9d7a4a3b1161708722566c043433b17dc8d22c9f1641915271c4bf908

Tx prefix hash: c28fb686da71ade3e1c6c4f591074bcf3eefe3414c551cddba0a0988765c5e4e
Tx public key: ceb893970124ae1f20e8ab4dbf05dee425e6343f556c857b2bb8db7e16bf9db5
Timestamp: 1727658116 Timestamp [UCT]: 2024-09-30 01:01:56 Age [y:d:h:m:s]: 00:103:05:29:10
Block: 1121046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73809 RingCT/type: yes/0
Extra: 01ceb893970124ae1f20e8ab4dbf05dee425e6343f556c857b2bb8db7e16bf9db502110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6abe7ceb89661cb894b88d6f7385b574691855dd3f63e8c731fbc75e89918fc4 0.600000000000 1603177 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": 1121056, "vin": [ { "gen": { "height": 1121046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6abe7ceb89661cb894b88d6f7385b574691855dd3f63e8c731fbc75e89918fc4" } } ], "extra": [ 1, 206, 184, 147, 151, 1, 36, 174, 31, 32, 232, 171, 77, 191, 5, 222, 228, 37, 230, 52, 63, 85, 108, 133, 123, 43, 184, 219, 126, 22, 191, 157, 181, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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