Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b5306ce4073dfc2a7e338895895af512063920c2dfe000c3b1652c92625a76f

Tx prefix hash: 9449ba6e7662b47fb4e31dfefb6b5e371952c6b0cc396d0250010f3e6fd983e7
Tx public key: 512eb4e488352e5bee049d1469de98e1fd4bfc4ee3aa915774acaeb5535a0863
Timestamp: 1710694400 Timestamp [UCT]: 2024-03-17 16:53:20 Age [y:d:h:m:s]: 01:013:19:10:25
Block: 980425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270829 RingCT/type: yes/0
Extra: 01512eb4e488352e5bee049d1469de98e1fd4bfc4ee3aa915774acaeb5535a086302110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea5f33720531cb119a9327cc769bcb26caa44fa3d91f50fb273f0b6200231ebb 0.600000000000 1440490 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": 980435, "vin": [ { "gen": { "height": 980425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea5f33720531cb119a9327cc769bcb26caa44fa3d91f50fb273f0b6200231ebb" } } ], "extra": [ 1, 81, 46, 180, 228, 136, 53, 46, 91, 238, 4, 157, 20, 105, 222, 152, 225, 253, 75, 252, 78, 227, 170, 145, 87, 116, 172, 174, 181, 83, 90, 8, 99, 2, 17, 0, 0, 0, 10, 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