Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765167d56213a52f017e11e8655bf31bb337a0f1f4935c02f7533273d6a95e8d

Tx prefix hash: fbed2818b2bbd2db302def793d0e99aa2f64afe09ab21a2bbede641615e4b737
Tx public key: 940adb99c716f3b8ef13646a8f50959df754e067bbec1391bed483adf72f36a0
Timestamp: 1701010804 Timestamp [UCT]: 2023-11-26 15:00:04 Age [y:d:h:m:s]: 01:194:15:59:57
Block: 900121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400344 RingCT/type: yes/0
Extra: 01940adb99c716f3b8ef13646a8f50959df754e067bbec1391bed483adf72f36a002110000000675e3f0e9000000000000000000

1 output(s) for total of 0.639036188000 dcy

stealth address amount amount idx
00: a2fa95611190d58964e58427fdd2a08cc28bcfd7a56a1f20eec2381139e874b7 0.639036188000 1356598 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": 900131, "vin": [ { "gen": { "height": 900121 } } ], "vout": [ { "amount": 639036188, "target": { "key": "a2fa95611190d58964e58427fdd2a08cc28bcfd7a56a1f20eec2381139e874b7" } } ], "extra": [ 1, 148, 10, 219, 153, 199, 22, 243, 184, 239, 19, 100, 106, 143, 80, 149, 157, 247, 84, 224, 103, 187, 236, 19, 145, 190, 212, 131, 173, 247, 47, 54, 160, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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