Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4d420b5236c870bc0713f572361db295dbe26144a6eb7b6b5cce102e2f9c772

Tx prefix hash: ddea9f7cad74c209b8f84cb9399303b1f712647af1fe0e54ec226c5ce6d518b5
Tx public key: 6c9487402a1835c8782112af706fdb164e2d2d688a1e38848886bbd139c20e90
Timestamp: 1703617748 Timestamp [UCT]: 2023-12-26 19:09:08 Age [y:d:h:m:s]: 01:099:04:12:57
Block: 921736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331993 RingCT/type: yes/0
Extra: 016c9487402a1835c8782112af706fdb164e2d2d688a1e38848886bbd139c20e9002110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0f2b86a3037c32b5d1f943a02dc8b4d0ebf4db6db2fadd1f59a97b7f3474c33 0.600000000000 1379430 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": 921746, "vin": [ { "gen": { "height": 921736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0f2b86a3037c32b5d1f943a02dc8b4d0ebf4db6db2fadd1f59a97b7f3474c33" } } ], "extra": [ 1, 108, 148, 135, 64, 42, 24, 53, 200, 120, 33, 18, 175, 112, 111, 219, 22, 78, 45, 45, 104, 138, 30, 56, 132, 136, 134, 187, 209, 57, 194, 14, 144, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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