Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e36f51b1b3113cfaa38073eaa09f3971453ab6a6fd3f1174befb0bcb58c418

Tx prefix hash: c3015d3bed99bcff3498f83418b0a4533574d41bd60a32eb4dd87849bf3c0a5a
Tx public key: eb6b25470dd8baa1da0ebdf6807a5120dc1024c5df1e8cb91959efb04644a76c
Timestamp: 1578663437 Timestamp [UCT]: 2020-01-10 13:37:17 Age [y:d:h:m:s]: 05:121:21:34:40
Block: 42735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1237097 RingCT/type: yes/0
Extra: 01eb6b25470dd8baa1da0ebdf6807a5120dc1024c5df1e8cb91959efb04644a76c0211000000128a2ee0d9000000000000000000

1 output(s) for total of 442.998288634000 dcy

stealth address amount amount idx
00: 8c59b81756d3c9a3546ca1781604a427e8c9f3a011124b21ab3df8094373879a 442.998288634000 77083 of 0

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": 42745, "vin": [ { "gen": { "height": 42735 } } ], "vout": [ { "amount": 442998288634, "target": { "key": "8c59b81756d3c9a3546ca1781604a427e8c9f3a011124b21ab3df8094373879a" } } ], "extra": [ 1, 235, 107, 37, 71, 13, 216, 186, 161, 218, 14, 189, 246, 128, 122, 81, 32, 220, 16, 36, 197, 223, 30, 140, 185, 25, 89, 239, 176, 70, 68, 167, 108, 2, 17, 0, 0, 0, 18, 138, 46, 224, 217, 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