Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05b9fb7f400cb1c27871e60386f162869fe95fadf387bac649142bd9c5e5ce10

Tx prefix hash: 62aed433abc8318da8d7883a0144dd4efefc0f058e7f666f6e49ff3f5d29d783
Tx public key: 7e35f37b363fefac5ba046ef214f388fbc6256b4fb45bda04cdef73b1a4c5967
Timestamp: 1725104218 Timestamp [UCT]: 2024-08-31 11:36:58 Age [y:d:h:m:s]: 00:278:09:54:16
Block: 1099870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198879 RingCT/type: yes/0
Extra: 017e35f37b363fefac5ba046ef214f388fbc6256b4fb45bda04cdef73b1a4c5967021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e153bf04a1cb9bc45bb6b5fc1d9a9a76de7c917de3b65be05b9cf6ceccac0e9e 0.600000000000 1575839 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": 1099880, "vin": [ { "gen": { "height": 1099870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e153bf04a1cb9bc45bb6b5fc1d9a9a76de7c917de3b65be05b9cf6ceccac0e9e" } } ], "extra": [ 1, 126, 53, 243, 123, 54, 63, 239, 172, 91, 160, 70, 239, 33, 79, 56, 143, 188, 98, 86, 180, 251, 69, 189, 160, 76, 222, 247, 59, 26, 76, 89, 103, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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