Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da305f818b7d3e7e2d9a20fea46c0d9ac1b1c55ac3d04c01af60049ec1391a58

Tx prefix hash: 6198d81fcee369415827a1dc9a1a98f7a722c2f8319ebd6a8251fcaebfedb2be
Tx public key: b0d37aced026a787cbd1297dd33a75f4b767b20d05133cd2b81f0641310a0f6a
Timestamp: 1711431751 Timestamp [UCT]: 2024-03-26 05:42:31 Age [y:d:h:m:s]: 01:009:13:19:38
Block: 986540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267776 RingCT/type: yes/0
Extra: 01b0d37aced026a787cbd1297dd33a75f4b767b20d05133cd2b81f0641310a0f6a02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f96bf7ad8a9825ec2fbeb660c1e4bf1919c3e11599bb84c77e9fdda60591ec1 0.600000000000 1446769 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": 986550, "vin": [ { "gen": { "height": 986540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f96bf7ad8a9825ec2fbeb660c1e4bf1919c3e11599bb84c77e9fdda60591ec1" } } ], "extra": [ 1, 176, 211, 122, 206, 208, 38, 167, 135, 203, 209, 41, 125, 211, 58, 117, 244, 183, 103, 178, 13, 5, 19, 60, 210, 184, 31, 6, 65, 49, 10, 15, 106, 2, 17, 0, 0, 0, 5, 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