Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 446d2b4d0d65c4abb8a51a65a5f7b1b58de97102def8d4d1a921f977e7e0465d

Tx prefix hash: 07b4e4e7d25b7487743bb20e41a81a7cd1abc43a1e334a1c2ec928506ed35a80
Tx public key: f72efc892c8951dfe5240f1d372c655b777c62c0d19ac7b33cfcef93d5367fe4
Timestamp: 1704715680 Timestamp [UCT]: 2024-01-08 12:08:00 Age [y:d:h:m:s]: 01:081:19:35:16
Block: 930823 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319578 RingCT/type: yes/0
Extra: 01f72efc892c8951dfe5240f1d372c655b777c62c0d19ac7b33cfcef93d5367fe402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7df02e2661b833d51f2192a2d105bd3c2b2a869cd32c77ae5c663d97523d1e1b 0.600000000000 1388713 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": 930833, "vin": [ { "gen": { "height": 930823 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7df02e2661b833d51f2192a2d105bd3c2b2a869cd32c77ae5c663d97523d1e1b" } } ], "extra": [ 1, 247, 46, 252, 137, 44, 137, 81, 223, 229, 36, 15, 29, 55, 44, 101, 91, 119, 124, 98, 192, 209, 154, 199, 179, 60, 252, 239, 147, 213, 54, 127, 228, 2, 17, 0, 0, 0, 1, 82, 212, 126, 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