Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68e2aa34b0e6dff327ae5afad7cb7ade1de86835ae5f3c5b2f0b921ec7f0afc1

Tx prefix hash: 12f9b4adb1ea679a53e33f1276e5c6e054d708ce5b2a21221867288ec8905807
Tx public key: f64ec8d9d592914f98fef7f6572ae327fd8bdcbb7815a3cc7d8455caa9f898de
Timestamp: 1733576659 Timestamp [UCT]: 2024-12-07 13:04:19 Age [y:d:h:m:s]: 00:114:01:51:50
Block: 1170009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81319 RingCT/type: yes/0
Extra: 01f64ec8d9d592914f98fef7f6572ae327fd8bdcbb7815a3cc7d8455caa9f898de021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 340cb7c46b202003dbfa4c4d3c7c38107db0afa8c2df427155cfccfb33fa814d 0.600000000000 1655736 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": 1170019, "vin": [ { "gen": { "height": 1170009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "340cb7c46b202003dbfa4c4d3c7c38107db0afa8c2df427155cfccfb33fa814d" } } ], "extra": [ 1, 246, 78, 200, 217, 213, 146, 145, 79, 152, 254, 247, 246, 87, 42, 227, 39, 253, 139, 220, 187, 120, 21, 163, 204, 125, 132, 85, 202, 169, 248, 152, 222, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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