Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf169475b998f37a77bda758179b6defce758a0a29df6792456767b5abaad5b4

Tx prefix hash: 7ebbc40d1f1870a2febe205ba6fa492aeeecd134350a192887a0b6a0987e553a
Tx public key: 3489aa2e0cc1571e6ef352d7af8fd2951333727f0f9588d7bbcddad8cdae2ea8
Timestamp: 1723797664 Timestamp [UCT]: 2024-08-16 08:41:04 Age [y:d:h:m:s]: 00:228:18:34:51
Block: 1089036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163370 RingCT/type: yes/0
Extra: 013489aa2e0cc1571e6ef352d7af8fd2951333727f0f9588d7bbcddad8cdae2ea802110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c056e7438e8ff5528ed10c35c83110865e6706705cdfa7a230de31c34a0f62e 0.600000000000 1563655 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": 1089046, "vin": [ { "gen": { "height": 1089036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c056e7438e8ff5528ed10c35c83110865e6706705cdfa7a230de31c34a0f62e" } } ], "extra": [ 1, 52, 137, 170, 46, 12, 193, 87, 30, 110, 243, 82, 215, 175, 143, 210, 149, 19, 51, 114, 127, 15, 149, 136, 215, 187, 205, 218, 216, 205, 174, 46, 168, 2, 17, 0, 0, 0, 11, 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