Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40d52f2f77fc2b50384d3edfa7272b5c48252d0bcce8847919b6ad7e82ab71a6

Tx prefix hash: 049f734c1edc18e6454ed4a637d9052695103ad647f1acc8694adc782280f4f8
Tx public key: 577f00b5d8b4115466c6a86e7f5088f3de2e232ee3fb357c7763f1162976624c
Timestamp: 1724114938 Timestamp [UCT]: 2024-08-20 00:48:58 Age [y:d:h:m:s]: 00:240:03:21:26
Block: 1091683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171485 RingCT/type: yes/0
Extra: 01577f00b5d8b4115466c6a86e7f5088f3de2e232ee3fb357c7763f1162976624c02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9b8ddafcd73f0530c01a630cde1b464e39810eaa47b2ed35473f82f1b0bee93 0.600000000000 1566316 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": 1091693, "vin": [ { "gen": { "height": 1091683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9b8ddafcd73f0530c01a630cde1b464e39810eaa47b2ed35473f82f1b0bee93" } } ], "extra": [ 1, 87, 127, 0, 181, 216, 180, 17, 84, 102, 198, 168, 110, 127, 80, 136, 243, 222, 46, 35, 46, 227, 251, 53, 124, 119, 99, 241, 22, 41, 118, 98, 76, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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