Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e4123fd49cdeab1a5b34417e451c5c9a467bfcefad40988a03d98d55376e144

Tx prefix hash: 008de01584b0559c9a3a26808c082d36e657c48b2da1102e5ebea7a836837add
Tx public key: 88eaa5c894d00a6fe388e93862e7758f64f9eef939ff37cdd6f1015866f2fc71
Timestamp: 1721249039 Timestamp [UCT]: 2024-07-17 20:43:59 Age [y:d:h:m:s]: 00:176:16:31:05
Block: 1067917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126413 RingCT/type: yes/0
Extra: 0188eaa5c894d00a6fe388e93862e7758f64f9eef939ff37cdd6f1015866f2fc7102110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5869f0c1691fd724449e4a69d843723ee134f0f4663bb401a7edce638fb29abd 0.600000000000 1538862 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": 1067927, "vin": [ { "gen": { "height": 1067917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5869f0c1691fd724449e4a69d843723ee134f0f4663bb401a7edce638fb29abd" } } ], "extra": [ 1, 136, 234, 165, 200, 148, 208, 10, 111, 227, 136, 233, 56, 98, 231, 117, 143, 100, 249, 238, 249, 57, 255, 55, 205, 214, 241, 1, 88, 102, 242, 252, 113, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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