Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2db6803bc0aa3a9dc8e242448baa364dfe6942dc983db6fc00acfdfbaa1e644

Tx prefix hash: 753d2a8d730fe1aeb314e3579ca3cdba92f9580c8b95e70b325c0ab6223dd435
Tx public key: 05141febc1fe4bf8759487c9ce7a76e69f4702ce810d088c752297118d664df2
Timestamp: 1704792501 Timestamp [UCT]: 2024-01-09 09:28:21 Age [y:d:h:m:s]: 01:105:21:16:49
Block: 931461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336798 RingCT/type: yes/0
Extra: 0105141febc1fe4bf8759487c9ce7a76e69f4702ce810d088c752297118d664df20211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3de7d0c96656dbbf11f584d308d1e87a591c19db7d3f58db398059764de401ea 0.600000000000 1389361 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": 931471, "vin": [ { "gen": { "height": 931461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3de7d0c96656dbbf11f584d308d1e87a591c19db7d3f58db398059764de401ea" } } ], "extra": [ 1, 5, 20, 31, 235, 193, 254, 75, 248, 117, 148, 135, 201, 206, 122, 118, 230, 159, 71, 2, 206, 129, 13, 8, 140, 117, 34, 151, 17, 141, 102, 77, 242, 2, 17, 0, 0, 0, 4, 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