Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90868cd7ca26787d854c0db0ad5b3e6a7f83244a0debd23fdc1598a4f158246b

Tx prefix hash: de129f29fc92d9696d712f0c2b4354b2144c67c09be84194492f71f7671d71dd
Tx public key: fbdd8379da7b41fa9437dc3cd1b8605d0c0532b7633e2105c20e9b7cb232b11b
Timestamp: 1731871140 Timestamp [UCT]: 2024-11-17 19:19:00 Age [y:d:h:m:s]: 00:190:22:11:13
Block: 1155880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136306 RingCT/type: yes/0
Extra: 01fbdd8379da7b41fa9437dc3cd1b8605d0c0532b7633e2105c20e9b7cb232b11b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08c523afd8d5d6e21fc0d8e60bd9ee497049530b165027001a841d1900adf9da 0.600000000000 1641499 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": 1155890, "vin": [ { "gen": { "height": 1155880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08c523afd8d5d6e21fc0d8e60bd9ee497049530b165027001a841d1900adf9da" } } ], "extra": [ 1, 251, 221, 131, 121, 218, 123, 65, 250, 148, 55, 220, 60, 209, 184, 96, 93, 12, 5, 50, 183, 99, 62, 33, 5, 194, 14, 155, 124, 178, 50, 177, 27, 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