Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d432a72e5c74cb22552fdc06ba99db5cba7c9e4042d6b4a990f19f370f16f4aa

Tx prefix hash: 9fe51510f2f5344b051b5794d4f3325aa703303fa9846019e8f9549dd09498e0
Tx public key: 4e11d173aa2991bfa0b4ad7c6be7a8fc94baa57cfc2252c43141a9ead59920b9
Timestamp: 1710564728 Timestamp [UCT]: 2024-03-16 04:52:08 Age [y:d:h:m:s]: 01:009:19:12:55
Block: 979351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267956 RingCT/type: yes/0
Extra: 014e11d173aa2991bfa0b4ad7c6be7a8fc94baa57cfc2252c43141a9ead59920b902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 008629d92feef6fc0bcc18dee64d1024083909a68f8ad8d7e72352c6c9e00d2e 0.600000000000 1439384 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": 979361, "vin": [ { "gen": { "height": 979351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "008629d92feef6fc0bcc18dee64d1024083909a68f8ad8d7e72352c6c9e00d2e" } } ], "extra": [ 1, 78, 17, 209, 115, 170, 41, 145, 191, 160, 180, 173, 124, 107, 231, 168, 252, 148, 186, 165, 124, 252, 34, 82, 196, 49, 65, 169, 234, 213, 153, 32, 185, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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