Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82837e377cf36615dcf94ce54cc3781895b1a15af4a2d0ae3a1e757688570361

Tx prefix hash: d1cb7ed432c35a5a8240bfc576f6ffa61e8ae0fa38e2531fdbace527a2fdd010
Tx public key: 976f210fad314d6e1cc95b173e316b986eff0f4de86a76358856ae4292ffd577
Timestamp: 1706693077 Timestamp [UCT]: 2024-01-31 09:24:37 Age [y:d:h:m:s]: 00:231:16:25:49
Block: 947214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165970 RingCT/type: yes/0
Extra: 01976f210fad314d6e1cc95b173e316b986eff0f4de86a76358856ae4292ffd57702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38b0b7159b6aeb9b62e023e9e54dc99f2f9e0e71aadbf4a5a90f88ea6a0885aa 0.600000000000 1405562 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": 947224, "vin": [ { "gen": { "height": 947214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38b0b7159b6aeb9b62e023e9e54dc99f2f9e0e71aadbf4a5a90f88ea6a0885aa" } } ], "extra": [ 1, 151, 111, 33, 15, 173, 49, 77, 110, 28, 201, 91, 23, 62, 49, 107, 152, 110, 255, 15, 77, 232, 106, 118, 53, 136, 86, 174, 66, 146, 255, 213, 119, 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