Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 725f92fc004feb3db4e0c156a6d69fcd6bcc3a1e2832d5dc58d6a5bb2d27c0a4

Tx prefix hash: 378e70b42dde4a5ec522b8fe312e87f40fc42bed130e3c9074ece3c13e70ac88
Tx public key: a2e7fbf9ae6a0682f283e6da9086a8520fda054c7ffb7aada3432b0b3536bf3f
Timestamp: 1727389516 Timestamp [UCT]: 2024-09-26 22:25:16 Age [y:d:h:m:s]: 00:058:15:18:38
Block: 1118816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41908 RingCT/type: yes/0
Extra: 01a2e7fbf9ae6a0682f283e6da9086a8520fda054c7ffb7aada3432b0b3536bf3f021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 691af4c04551ef9eb050aef6baafb53dd4bcd861c9d5f1daddc6bea3e9eb4081 0.600000000000 1600141 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": 1118826, "vin": [ { "gen": { "height": 1118816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "691af4c04551ef9eb050aef6baafb53dd4bcd861c9d5f1daddc6bea3e9eb4081" } } ], "extra": [ 1, 162, 231, 251, 249, 174, 106, 6, 130, 242, 131, 230, 218, 144, 134, 168, 82, 15, 218, 5, 76, 127, 251, 122, 173, 163, 67, 43, 11, 53, 54, 191, 63, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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