Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb1a455f2eaf4a64f9e3aa2fef8ab4f77d070645dfa44f1cac8f6f13c325c3c1

Tx prefix hash: 781d8074f0e8283971f4e759b6c308d901126e66a5be4b5583ea735883210a57
Tx public key: 8741a17153f1a53d32a2073fb8dd5009c624d4ef7622869ab3f1f42ac2ebad15
Timestamp: 1697398573 Timestamp [UCT]: 2023-10-15 19:36:13 Age [y:d:h:m:s]: 01:182:17:30:12
Block: 870380 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391625 RingCT/type: yes/0
Extra: 018741a17153f1a53d32a2073fb8dd5009c624d4ef7622869ab3f1f42ac2ebad1502110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.801806873000 dcy

stealth address amount amount idx
00: cfbb17293a6ad7382c023c4d3fcb27fcd462a67757c4594c281108d85f1ed7ab 0.801806873000 1325259 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": 870390, "vin": [ { "gen": { "height": 870380 } } ], "vout": [ { "amount": 801806873, "target": { "key": "cfbb17293a6ad7382c023c4d3fcb27fcd462a67757c4594c281108d85f1ed7ab" } } ], "extra": [ 1, 135, 65, 161, 113, 83, 241, 165, 61, 50, 162, 7, 63, 184, 221, 80, 9, 198, 36, 212, 239, 118, 34, 134, 154, 179, 241, 244, 42, 194, 235, 173, 21, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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