Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37c92e31830ef65cae7d2287ed19dc3e357708f386a40fcf583b75cf291a09df

Tx prefix hash: 51fa6f34d1b2a172ec0cff5c27a1cfa4ab03895e6982eaaa913c38b9938b87c1
Tx public key: f3814d754f87355ba7a5e1eee7d0a4aedc1cda6257640ae58aad360fe9fafac3
Timestamp: 1706073745 Timestamp [UCT]: 2024-01-24 05:22:25 Age [y:d:h:m:s]: 01:147:00:44:29
Block: 942068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366082 RingCT/type: yes/0
Extra: 01f3814d754f87355ba7a5e1eee7d0a4aedc1cda6257640ae58aad360fe9fafac302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5cd1d80ed944918184546fa5dd9a3d302183c85ed9e1b80f23b2ddc90060f3a 0.600000000000 1400234 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": 942078, "vin": [ { "gen": { "height": 942068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5cd1d80ed944918184546fa5dd9a3d302183c85ed9e1b80f23b2ddc90060f3a" } } ], "extra": [ 1, 243, 129, 77, 117, 79, 135, 53, 91, 167, 165, 225, 238, 231, 208, 164, 174, 220, 28, 218, 98, 87, 100, 10, 229, 138, 173, 54, 15, 233, 250, 250, 195, 2, 17, 0, 0, 0, 2, 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