Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549d621c6f838730dd80f611d4c112c1091ad6fcf24dc24b6e714ec22b643c1d

Tx prefix hash: a0f0179b07d3e84b206745dc3571fceb39939db1af5def94079a982856358db9
Tx public key: 0a4aa497c15255334199b6834c3833524dac92db5786912f761cda0ab44a4b0d
Timestamp: 1702148420 Timestamp [UCT]: 2023-12-09 19:00:20 Age [y:d:h:m:s]: 01:332:21:54:49
Block: 909560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496774 RingCT/type: yes/0
Extra: 010a4aa497c15255334199b6834c3833524dac92db5786912f761cda0ab44a4b0d02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600030000000 dcy

stealth address amount amount idx
00: 377bf1cb826d7a063b83b8d9f3af80cdb852ba1cea63766f223d2e38f324fba8 0.600030000000 1366657 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": 909570, "vin": [ { "gen": { "height": 909560 } } ], "vout": [ { "amount": 600030000, "target": { "key": "377bf1cb826d7a063b83b8d9f3af80cdb852ba1cea63766f223d2e38f324fba8" } } ], "extra": [ 1, 10, 74, 164, 151, 193, 82, 85, 51, 65, 153, 182, 131, 76, 56, 51, 82, 77, 172, 146, 219, 87, 134, 145, 47, 118, 28, 218, 10, 180, 74, 75, 13, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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