Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 679f5d66550e151eb66622534f110791b7cce2a7b8410b4dc6690862e5ca1118

Tx prefix hash: d31310cb004f1a0c0337ce7f6a1d58e410eb5247eba10c9c7f660169e20c8f3b
Tx public key: 90776f511924e237f85844d16919fa9c0740595e8adcc3ad4bfd25330d4daa3d
Timestamp: 1725936398 Timestamp [UCT]: 2024-09-10 02:46:38 Age [y:d:h:m:s]: 00:121:02:23:44
Block: 1106773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86602 RingCT/type: yes/0
Extra: 0190776f511924e237f85844d16919fa9c0740595e8adcc3ad4bfd25330d4daa3d021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b7ad1117d502df14d63fbdb2cd9646ffb7879ea0d063abb57e4dd4c7c4150dc 0.600000000000 1584374 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": 1106783, "vin": [ { "gen": { "height": 1106773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b7ad1117d502df14d63fbdb2cd9646ffb7879ea0d063abb57e4dd4c7c4150dc" } } ], "extra": [ 1, 144, 119, 111, 81, 25, 36, 226, 55, 248, 88, 68, 209, 105, 25, 250, 156, 7, 64, 89, 94, 138, 220, 195, 173, 75, 253, 37, 51, 13, 77, 170, 61, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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