Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 976070a7b2cc45945383ee8c80e8ee88e84ea334532c2199a495e7e2a4ce1dc8

Tx prefix hash: 64f8457eb56065987f7cf9f2ad3205d6d28039edf034beeed6c834e79922d7a9
Tx public key: f205099fa96418c8ec9b7a79c909c33ed96941450da70eff58ce2c8a7b5f1db0
Timestamp: 1713849619 Timestamp [UCT]: 2024-04-23 05:20:19 Age [y:d:h:m:s]: 00:195:15:42:57
Block: 1006570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140042 RingCT/type: yes/0
Extra: 01f205099fa96418c8ec9b7a79c909c33ed96941450da70eff58ce2c8a7b5f1db002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c0ad0ef8df3a804be30882ea5bfc700302585b0fd64ad3c70cdcc2bd14417c1 0.600000000000 1467636 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": 1006580, "vin": [ { "gen": { "height": 1006570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c0ad0ef8df3a804be30882ea5bfc700302585b0fd64ad3c70cdcc2bd14417c1" } } ], "extra": [ 1, 242, 5, 9, 159, 169, 100, 24, 200, 236, 155, 122, 121, 201, 9, 195, 62, 217, 105, 65, 69, 13, 167, 14, 255, 88, 206, 44, 138, 123, 95, 29, 176, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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