Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a01324f3fe973ead83910b34cbe8c59eacd8e8b48b63b52a671ba72f40700644

Tx prefix hash: 945a98de0dc434f08f84ee772bf3c175d68d50042b988debf0f5280ad49fe04d
Tx public key: a39ba8b1d769bd22cbf9b5b6b7179f49ecc7996df65d0add49683be7517f5932
Timestamp: 1736723665 Timestamp [UCT]: 2025-01-12 23:14:25 Age [y:d:h:m:s]: 00:305:09:38:01
Block: 1196056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215784 RingCT/type: yes/0
Extra: 01a39ba8b1d769bd22cbf9b5b6b7179f49ecc7996df65d0add49683be7517f593202110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf181a689e4fd45eb7bcc14c8cacffa87cf11b0cea96e0e0d3137de72d4b5a69 0.600000000000 1682653 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": 1196066, "vin": [ { "gen": { "height": 1196056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf181a689e4fd45eb7bcc14c8cacffa87cf11b0cea96e0e0d3137de72d4b5a69" } } ], "extra": [ 1, 163, 155, 168, 177, 215, 105, 189, 34, 203, 249, 181, 182, 183, 23, 159, 73, 236, 199, 153, 109, 246, 93, 10, 221, 73, 104, 59, 231, 81, 127, 89, 50, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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