Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b14d837c73e1cc8d14dc0decdcbf3b44592e477c089462c293462189d28c776f

Tx prefix hash: ca1f8553df72dedabfae332c6b0e08544b64505723310ae3579dff082d8853cd
Tx public key: de6e32a3f7a25a6e8f91d4f224a88ffeec74e9671408e9cc853824c05ac60f41
Timestamp: 1662189094 Timestamp [UCT]: 2022-09-03 07:11:34 Age [y:d:h:m:s]: 02:201:01:13:56
Block: 579779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 664930 RingCT/type: yes/0
Extra: 01de6e32a3f7a25a6e8f91d4f224a88ffeec74e9671408e9cc853824c05ac60f4102110000000d33af99f4000000000000000000

1 output(s) for total of 7.361250281000 dcy

stealth address amount amount idx
00: a86c44e73800ee86b4d48361cf9c69566c0d4d3394e2a776b66f289772f902fd 7.361250281000 1013265 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": 579789, "vin": [ { "gen": { "height": 579779 } } ], "vout": [ { "amount": 7361250281, "target": { "key": "a86c44e73800ee86b4d48361cf9c69566c0d4d3394e2a776b66f289772f902fd" } } ], "extra": [ 1, 222, 110, 50, 163, 247, 162, 90, 110, 143, 145, 212, 242, 36, 168, 143, 254, 236, 116, 233, 103, 20, 8, 233, 204, 133, 56, 36, 192, 90, 198, 15, 65, 2, 17, 0, 0, 0, 13, 51, 175, 153, 244, 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