Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 129c301eb9fa8c525c9c149edc9860b1398db6a20f51a69e72ac0312cd15284e

Tx prefix hash: ef278a6b89ef72080f73788e98aa7fe317f5c4564697e9f28ecf1728354b5c22
Tx public key: 6e0ad99d336cb4e19c694eb4b8b2479cc746d09fba41bab7f919a7cee70f4628
Timestamp: 1711749503 Timestamp [UCT]: 2024-03-29 21:58:23 Age [y:d:h:m:s]: 01:078:15:00:55
Block: 989171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317080 RingCT/type: yes/0
Extra: 016e0ad99d336cb4e19c694eb4b8b2479cc746d09fba41bab7f919a7cee70f46280211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 165e429ab2a19b670598ade649bd513f4040753b2022bb584042cb8d1f88a51e 0.600000000000 1449466 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": 989181, "vin": [ { "gen": { "height": 989171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "165e429ab2a19b670598ade649bd513f4040753b2022bb584042cb8d1f88a51e" } } ], "extra": [ 1, 110, 10, 217, 157, 51, 108, 180, 225, 156, 105, 78, 180, 184, 178, 71, 156, 199, 70, 208, 159, 186, 65, 186, 183, 249, 25, 167, 206, 231, 15, 70, 40, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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