Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34a05c2405d36a36449fac99263c83c7e6ee8a45f701a8a2c25bcce50b1157c3

Tx prefix hash: 30f8a26fc148b7d0545128323f2ef27f47c4e5bc25519d086d60e9288057b128
Tx public key: ea6a92a86e039085c8e2e7344e83846c65af76e5a72e8b8562c6b40eab09ef77
Timestamp: 1734834238 Timestamp [UCT]: 2024-12-22 02:23:58 Age [y:d:h:m:s]: 00:107:20:41:02
Block: 1180450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76841 RingCT/type: yes/0
Extra: 01ea6a92a86e039085c8e2e7344e83846c65af76e5a72e8b8562c6b40eab09ef77021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1c1deeba20a5a656359198feab9f0441f60d33dbdda5b495b0b34853a96e488 0.600000000000 1666861 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": 1180460, "vin": [ { "gen": { "height": 1180450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1c1deeba20a5a656359198feab9f0441f60d33dbdda5b495b0b34853a96e488" } } ], "extra": [ 1, 234, 106, 146, 168, 110, 3, 144, 133, 200, 226, 231, 52, 78, 131, 132, 108, 101, 175, 118, 229, 167, 46, 139, 133, 98, 198, 180, 14, 171, 9, 239, 119, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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