Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27afdbbe530bf379bcda3eeccb3253c8436606f2b54fe0e49aece08f7895b096

Tx prefix hash: bae85966d7cf76c82a9e92fd05d3cc85748a0e58bffd1f7106c2938445fd747e
Tx public key: 827d0bbd5ef5e38ccc80bd3e47deaeaf534956e2d3d77387833b6e358a2bb591
Timestamp: 1639013157 Timestamp [UCT]: 2021-12-09 01:25:57 Age [y:d:h:m:s]: 03:139:15:07:35
Block: 391449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 878541 RingCT/type: yes/0
Extra: 01827d0bbd5ef5e38ccc80bd3e47deaeaf534956e2d3d77387833b6e358a2bb59102110000000706faf294000000000000000000

1 output(s) for total of 30.971862942000 dcy

stealth address amount amount idx
00: 7d6b72964ea2e33c24fdacafb27d6a0563a3e5e4bb4decb52658037dab8a8f44 30.971862942000 787852 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": 391459, "vin": [ { "gen": { "height": 391449 } } ], "vout": [ { "amount": 30971862942, "target": { "key": "7d6b72964ea2e33c24fdacafb27d6a0563a3e5e4bb4decb52658037dab8a8f44" } } ], "extra": [ 1, 130, 125, 11, 189, 94, 245, 227, 140, 204, 128, 189, 62, 71, 222, 174, 175, 83, 73, 86, 226, 211, 215, 115, 135, 131, 59, 110, 53, 138, 43, 181, 145, 2, 17, 0, 0, 0, 7, 6, 250, 242, 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