Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2eccc4b4618b233403794556c040c4588a3476025f44b2d1409a27dc82bfa2fd

Tx prefix hash: 764f8efa1796e338f6b2fa1c7654a5043ebcde76e18e2e0a61335a0f9ea881de
Tx public key: 95beb36f2ebfe7be65ad8cefa14bd814630c26b00246effb22b6f174057908d4
Timestamp: 1709218089 Timestamp [UCT]: 2024-02-29 14:48:09 Age [y:d:h:m:s]: 01:253:08:41:58
Block: 968175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439797 RingCT/type: yes/0
Extra: 0195beb36f2ebfe7be65ad8cefa14bd814630c26b00246effb22b6f174057908d402110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ecec785f7d373ce5ff8b16f597a16cefe7e812689f8e0452411ee5a8db2e5c4 0.600000000000 1427976 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": 968185, "vin": [ { "gen": { "height": 968175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ecec785f7d373ce5ff8b16f597a16cefe7e812689f8e0452411ee5a8db2e5c4" } } ], "extra": [ 1, 149, 190, 179, 111, 46, 191, 231, 190, 101, 173, 140, 239, 161, 75, 216, 20, 99, 12, 38, 176, 2, 70, 239, 251, 34, 182, 241, 116, 5, 121, 8, 212, 2, 17, 0, 0, 0, 9, 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