Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9a05bf0028191ad5769b505a4262b13f8f8acab35020555b496730d19c6e761

Tx prefix hash: 4da4cc9bc52f90202438744f2cb964e2837ea584001352dbaa1cf6d79b417084
Tx public key: a93558e7ca1949795ace6cb2dbb0b2e0b6b55e535ee5dc8d301b19a76a087e79
Timestamp: 1663673263 Timestamp [UCT]: 2022-09-20 11:27:43 Age [y:d:h:m:s]: 02:181:00:14:36
Block: 591911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 650766 RingCT/type: yes/0
Extra: 01a93558e7ca1949795ace6cb2dbb0b2e0b6b55e535ee5dc8d301b19a76a087e7902110000000675e3f0e9000000000000000000

1 output(s) for total of 6.710474258000 dcy

stealth address amount amount idx
00: 2a84ec9904790867319a76fc8d512228f51841510bd7297ca809ffd7b0db4ba7 6.710474258000 1026517 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": 591921, "vin": [ { "gen": { "height": 591911 } } ], "vout": [ { "amount": 6710474258, "target": { "key": "2a84ec9904790867319a76fc8d512228f51841510bd7297ca809ffd7b0db4ba7" } } ], "extra": [ 1, 169, 53, 88, 231, 202, 25, 73, 121, 90, 206, 108, 178, 219, 176, 178, 224, 182, 181, 94, 83, 94, 229, 220, 141, 48, 27, 25, 167, 106, 8, 126, 121, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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