Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc194c8317d7eed6108e742f75d0c35d0bf4bf151cf5db71a88731fe0304c7d7

Tx prefix hash: 33c15f144a37387b1cb111ae18b85e49680c3668e821fc750ab5582066092d13
Tx public key: b4b7a7ced86a376d5c266364c18e87367802ea8e9a805fd0cf948cc59ae6496e
Timestamp: 1712570523 Timestamp [UCT]: 2024-04-08 10:02:03 Age [y:d:h:m:s]: 00:341:23:31:30
Block: 995934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244536 RingCT/type: yes/0
Extra: 01b4b7a7ced86a376d5c266364c18e87367802ea8e9a805fd0cf948cc59ae6496e02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9445781d96b808c7f1a520a495f2913cb8af4bdd016b39b5a40ec071b7444841 0.600000000000 1456350 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": 995944, "vin": [ { "gen": { "height": 995934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9445781d96b808c7f1a520a495f2913cb8af4bdd016b39b5a40ec071b7444841" } } ], "extra": [ 1, 180, 183, 167, 206, 216, 106, 55, 109, 92, 38, 99, 100, 193, 142, 135, 54, 120, 2, 234, 142, 154, 128, 95, 208, 207, 148, 140, 197, 154, 230, 73, 110, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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