Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b263eaa1af3537e5c20c025df004419928ecc2f587b6dc7b30f6c2da47bc21c0

Tx prefix hash: 6b16cf0d46e42008797af720ef8cc59614a8a1446cd0555bba6557cf480ff936
Tx public key: f21e2e18018692b76bc7d6ce10a16fe6c9e7cb736ccec9286608c3869b280281
Timestamp: 1681615836 Timestamp [UCT]: 2023-04-16 03:30:36 Age [y:d:h:m:s]: 02:000:15:53:54
Block: 739569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522625 RingCT/type: yes/0
Extra: 01f21e2e18018692b76bc7d6ce10a16fe6c9e7cb736ccec9286608c3869b280281021100000001b3164c24000000000000000000

1 output(s) for total of 2.175209602000 dcy

stealth address amount amount idx
00: 3a35e28e396f16629e093f48480ec8e731ee1d7f6422a50de51f3b2193e725aa 2.175209602000 1186426 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": 739579, "vin": [ { "gen": { "height": 739569 } } ], "vout": [ { "amount": 2175209602, "target": { "key": "3a35e28e396f16629e093f48480ec8e731ee1d7f6422a50de51f3b2193e725aa" } } ], "extra": [ 1, 242, 30, 46, 24, 1, 134, 146, 183, 107, 199, 214, 206, 16, 161, 111, 230, 201, 231, 203, 115, 108, 206, 201, 40, 102, 8, 195, 134, 155, 40, 2, 129, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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