Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48996192a9886c3693800f4910c5e20317ffebcca5fcee9b2f0098967b4ff306

Tx prefix hash: e6d0965b9945ef42ea42608ec1eef74e90e314b28d3f02d5c8f9e37929f02ebf
Tx public key: 411c1c4ecdf837811ce05a1c6e508abbf63cd43e90e76ea394a7688806977d2f
Timestamp: 1702760288 Timestamp [UCT]: 2023-12-16 20:58:08 Age [y:d:h:m:s]: 01:035:00:53:21
Block: 914630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286357 RingCT/type: yes/0
Extra: 01411c1c4ecdf837811ce05a1c6e508abbf63cd43e90e76ea394a7688806977d2f021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d91c0cf275f508f7aab5d11b222cf7ad40ec310951e2ba2934fcd749891a6d31 0.600000000000 1371980 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": 914640, "vin": [ { "gen": { "height": 914630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d91c0cf275f508f7aab5d11b222cf7ad40ec310951e2ba2934fcd749891a6d31" } } ], "extra": [ 1, 65, 28, 28, 78, 205, 248, 55, 129, 28, 224, 90, 28, 110, 80, 138, 187, 246, 60, 212, 62, 144, 231, 110, 163, 148, 167, 104, 136, 6, 151, 125, 47, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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