Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 115aa54a86fca4136a80b36e6aa47d54eed695a3d38f6dae87cff8f7baff025d

Tx prefix hash: bf331b130e1b3bd49013b3d340af731587c63b5f74954fab84813acf8a27c32f
Tx public key: b85d3b7c2b194400ba3c8b745e18360df7b8a89bdb95d0f2e457a69d133c40d6
Timestamp: 1673189631 Timestamp [UCT]: 2023-01-08 14:53:51 Age [y:d:h:m:s]: 02:299:23:39:22
Block: 670328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733796 RingCT/type: yes/0
Extra: 01b85d3b7c2b194400ba3c8b745e18360df7b8a89bdb95d0f2e457a69d133c40d602110000000252542ceb000000000000000000

1 output(s) for total of 3.689139063000 dcy

stealth address amount amount idx
00: 1cde50783b5c987d7dd2297d1eb9e16f64d1c2391cb54f9b7f26808f06c7435b 3.689139063000 1111723 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": 670338, "vin": [ { "gen": { "height": 670328 } } ], "vout": [ { "amount": 3689139063, "target": { "key": "1cde50783b5c987d7dd2297d1eb9e16f64d1c2391cb54f9b7f26808f06c7435b" } } ], "extra": [ 1, 184, 93, 59, 124, 43, 25, 68, 0, 186, 60, 139, 116, 94, 24, 54, 13, 247, 184, 168, 155, 219, 149, 208, 242, 228, 87, 166, 157, 19, 60, 64, 214, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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