Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 911aa9323f7438b27e57c505afce4ba84afe0e4f35e57e083e690da4096b7618

Tx prefix hash: 01855b3ef3f193302f070a752b6702a4b8645ba0f91bab94e242f063555c621f
Tx public key: ca93dd354bcc61535db38e4f05c2ee5fad348faef851239d06218a7abddc8b88
Timestamp: 1720071529 Timestamp [UCT]: 2024-07-04 05:38:49 Age [y:d:h:m:s]: 00:233:06:13:02
Block: 1058141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166612 RingCT/type: yes/0
Extra: 01ca93dd354bcc61535db38e4f05c2ee5fad348faef851239d06218a7abddc8b8802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bcdc5844c057d8c237ff1c3bc24eec8c6b587bb366c1548a59e7c8e9e22407b 0.600000000000 1528590 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": 1058151, "vin": [ { "gen": { "height": 1058141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bcdc5844c057d8c237ff1c3bc24eec8c6b587bb366c1548a59e7c8e9e22407b" } } ], "extra": [ 1, 202, 147, 221, 53, 75, 204, 97, 83, 93, 179, 142, 79, 5, 194, 238, 95, 173, 52, 143, 174, 248, 81, 35, 157, 6, 33, 138, 122, 189, 220, 139, 136, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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