Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69d595036a4a7accb430daae6c4f2d6376bf0db8d8bccee8d30711498aecb8b6

Tx prefix hash: dfb39e1c9778b7a61af93163b89d3d473d10691eef9c47c58b552be4904ef691
Tx public key: 8ac2d9fe49eaece0bccea328bef68e1005a9c786be68c1624d73c7634c71cbb2
Timestamp: 1747814517 Timestamp [UCT]: 2025-05-21 08:01:57 Age [y:d:h:m:s]: 00:216:02:31:49
Block: 1287624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152171 RingCT/type: yes/0
Extra: 018ac2d9fe49eaece0bccea328bef68e1005a9c786be68c1624d73c7634c71cbb20211000000091f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f94cc7f4bb1732489f38065b2ae33ed5973b1a519ebb6dfe7519886705ed5c8 0.600000000000 1775091 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": 1287634, "vin": [ { "gen": { "height": 1287624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f94cc7f4bb1732489f38065b2ae33ed5973b1a519ebb6dfe7519886705ed5c8" } } ], "extra": [ 1, 138, 194, 217, 254, 73, 234, 236, 224, 188, 206, 163, 40, 190, 246, 142, 16, 5, 169, 199, 134, 190, 104, 193, 98, 77, 115, 199, 99, 76, 113, 203, 178, 2, 17, 0, 0, 0, 9, 31, 144, 81, 122, 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