Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6731c272ecb060775f8bd134ca77d8aca4d825641f1f71738c2d86c400e3509

Tx prefix hash: 024d73e829b5e385375a2eff7341d5e5635be2738aa005ee259d674132661c0f
Tx public key: ede5134f474d58f831ef745f5fa0b21cae4934b519ab83da72d7b9a4a26b0bb4
Timestamp: 1701208241 Timestamp [UCT]: 2023-11-28 21:50:41 Age [y:d:h:m:s]: 01:055:03:15:36
Block: 901773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300738 RingCT/type: yes/0
Extra: 01ede5134f474d58f831ef745f5fa0b21cae4934b519ab83da72d7b9a4a26b0bb402110000000133af99f4000000000000000000

1 output(s) for total of 0.631032443000 dcy

stealth address amount amount idx
00: 7f91d5fba258282f00c706f714abd61631dc9cf2aea06fe8d07547ce4ccbbaf7 0.631032443000 1358364 of 0

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": 901783, "vin": [ { "gen": { "height": 901773 } } ], "vout": [ { "amount": 631032443, "target": { "key": "7f91d5fba258282f00c706f714abd61631dc9cf2aea06fe8d07547ce4ccbbaf7" } } ], "extra": [ 1, 237, 229, 19, 79, 71, 77, 88, 248, 49, 239, 116, 95, 95, 160, 178, 28, 174, 73, 52, 181, 25, 171, 131, 218, 114, 215, 185, 164, 162, 107, 11, 180, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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