Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 36e48c6403b5f1e8aaa0ea77cf62164b9d49935dfe7c9b043b8c6a703e363dbd

Tx prefix hash: 03264d076f2dd4de62c71365b5f769fd9d02152723515720306d576e37170bf4
Tx public key: 97b8f8771e59968c9029c2ffe8d528d819ead73ccfbe934017c38dc0a2c3e5e6
Timestamp: 1705103907 Timestamp [UCT]: 2024-01-12 23:58:27 Age [y:d:h:m:s]: 01:066:10:30:01
Block: 934039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308604 RingCT/type: yes/0
Extra: 0197b8f8771e59968c9029c2ffe8d528d819ead73ccfbe934017c38dc0a2c3e5e60211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ea16aef85c1f1ac00d359e553a422217ef9d8f2c3420030c13a4a4143e2b7d0 0.600000000000 1392025 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": 934049, "vin": [ { "gen": { "height": 934039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ea16aef85c1f1ac00d359e553a422217ef9d8f2c3420030c13a4a4143e2b7d0" } } ], "extra": [ 1, 151, 184, 248, 119, 30, 89, 150, 140, 144, 41, 194, 255, 232, 213, 40, 216, 25, 234, 215, 60, 207, 190, 147, 64, 23, 195, 141, 192, 162, 195, 229, 230, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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