Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5472a3cd79ccac5294ccf568d9faceb381a3b174ef058c5051a88669ab1bfba6

Tx prefix hash: ee2bc3d50072fa983634c536586535f07e6c49fdc7c8697967e40f225a9e209d
Tx public key: c37f5006e4f2dcedfc9bfef0a303d3750ef12c4318cd72cbfe69b69129794e0c
Timestamp: 1577553209 Timestamp [UCT]: 2019-12-28 17:13:29 Age [y:d:h:m:s]: 05:077:02:44:34
Block: 33637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1204992 RingCT/type: yes/0
Extra: 01c37f5006e4f2dcedfc9bfef0a303d3750ef12c4318cd72cbfe69b69129794e0c021100000012398c17aa000000000000000000

1 output(s) for total of 474.840236450000 dcy

stealth address amount amount idx
00: b15e63ef12904061b24751fa76510d6d98e2b6f46141f3491360f0f7a2a20e9a 474.840236450000 56407 of 0

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": 33647, "vin": [ { "gen": { "height": 33637 } } ], "vout": [ { "amount": 474840236450, "target": { "key": "b15e63ef12904061b24751fa76510d6d98e2b6f46141f3491360f0f7a2a20e9a" } } ], "extra": [ 1, 195, 127, 80, 6, 228, 242, 220, 237, 252, 155, 254, 240, 163, 3, 211, 117, 14, 241, 44, 67, 24, 205, 114, 203, 254, 105, 182, 145, 41, 121, 78, 12, 2, 17, 0, 0, 0, 18, 57, 140, 23, 170, 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