Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1df6aa39a3c9cf25fcb077b674ac971f24c89cc9c69e64a669e4e0c64a044a9

Tx prefix hash: f5063368effb9c2f9b7db63777258c99d957f6c4b192121cdf5eb3857abbf786
Tx public key: 0d3061ba7af28f75979403dbc004ea6df1b0752ce86348159e361f8733bfec76
Timestamp: 1701751745 Timestamp [UCT]: 2023-12-05 04:49:05 Age [y:d:h:m:s]: 01:121:00:27:52
Block: 906254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347651 RingCT/type: yes/0
Extra: 010d3061ba7af28f75979403dbc004ea6df1b0752ce86348159e361f8733bfec760211000000014b8f5122000000000000000000

1 output(s) for total of 0.609823657000 dcy

stealth address amount amount idx
00: 1137da38c7bf706b1cfd9ffc7266c8898bd230553f19b935b312d8c960396e9a 0.609823657000 1363181 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": 906264, "vin": [ { "gen": { "height": 906254 } } ], "vout": [ { "amount": 609823657, "target": { "key": "1137da38c7bf706b1cfd9ffc7266c8898bd230553f19b935b312d8c960396e9a" } } ], "extra": [ 1, 13, 48, 97, 186, 122, 242, 143, 117, 151, 148, 3, 219, 192, 4, 234, 109, 241, 176, 117, 44, 232, 99, 72, 21, 158, 54, 31, 135, 51, 191, 236, 118, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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