Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b83e1d770ff2e1dff5962f977437709e8eda234c2ac4d7aded542a782c59e16e

Tx prefix hash: 60264bd1552af07f9bdfbed95f917f2a4107fbb9c3f5cca3dd78183ed4b2d15d
Tx public key: 0c1d1945f25e1c9f6ba950ee03019c71f1d026e7042bbd7ad1e8afc4b3544ebd
Timestamp: 1717341932 Timestamp [UCT]: 2024-06-02 15:25:32 Age [y:d:h:m:s]: 01:159:00:23:05
Block: 1035525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372219 RingCT/type: yes/0
Extra: 010c1d1945f25e1c9f6ba950ee03019c71f1d026e7042bbd7ad1e8afc4b3544ebd02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16884e4eb8832bcdf4a62dba139f791664f155b2b902ccfdd312860ed11c8bb0 0.600000000000 1504046 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": 1035535, "vin": [ { "gen": { "height": 1035525 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16884e4eb8832bcdf4a62dba139f791664f155b2b902ccfdd312860ed11c8bb0" } } ], "extra": [ 1, 12, 29, 25, 69, 242, 94, 28, 159, 107, 169, 80, 238, 3, 1, 156, 113, 241, 208, 38, 231, 4, 43, 189, 122, 209, 232, 175, 196, 179, 84, 78, 189, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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