Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 415fe1283714d052b109df8f862cfa9ebc0842761a7cb1858f01807561ddb95e

Tx prefix hash: 7cfd94ae72df09677cc9d296d41faa2581c35754c54627f098d7a1398ae8c2f5
Tx public key: cec9fafd89d255c4e4d2893d548536dcb4bfbcd264240cd15a89e858e52f2b34
Timestamp: 1705957106 Timestamp [UCT]: 2024-01-22 20:58:26 Age [y:d:h:m:s]: 01:079:02:00:56
Block: 941098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317627 RingCT/type: yes/0
Extra: 01cec9fafd89d255c4e4d2893d548536dcb4bfbcd264240cd15a89e858e52f2b3402110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d96f7f68c77ec4d060cbfe7c65305586ca7919d89b909c4fb56ed7db154c0f53 0.600000000000 1399240 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": 941108, "vin": [ { "gen": { "height": 941098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d96f7f68c77ec4d060cbfe7c65305586ca7919d89b909c4fb56ed7db154c0f53" } } ], "extra": [ 1, 206, 201, 250, 253, 137, 210, 85, 196, 228, 210, 137, 61, 84, 133, 54, 220, 180, 191, 188, 210, 100, 36, 12, 209, 90, 137, 232, 88, 229, 47, 43, 52, 2, 17, 0, 0, 0, 7, 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