Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 291cb2fa8e4042b00930bf3a727028e034ce96a24f963c6f630f4c58c31536b8

Tx prefix hash: 28be6509c89398d5080d44426338e88a32ac1ba3d430d1c9e9c69962abde8ce7
Tx public key: fc6e8b2660b6b2f6fc0856f094ae2414b811972d6a122a62b401a851892437c6
Timestamp: 1736112807 Timestamp [UCT]: 2025-01-05 21:33:27 Age [y:d:h:m:s]: 00:296:21:29:22
Block: 1191016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209675 RingCT/type: yes/0
Extra: 01fc6e8b2660b6b2f6fc0856f094ae2414b811972d6a122a62b401a851892437c602110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4f0ac62591846be55c924244bec795cf716ae381389e398de75f236a2c73c4d 0.600000000000 1677539 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": 1191026, "vin": [ { "gen": { "height": 1191016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4f0ac62591846be55c924244bec795cf716ae381389e398de75f236a2c73c4d" } } ], "extra": [ 1, 252, 110, 139, 38, 96, 182, 178, 246, 252, 8, 86, 240, 148, 174, 36, 20, 184, 17, 151, 45, 106, 18, 42, 98, 180, 1, 168, 81, 137, 36, 55, 198, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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